Owning A Mistake In The First Hour
It is 9:40 on a Tuesday, and Ted has just found the error.
The pricing sheet he sent to the client on Friday has a formula pulling from the wrong column. Two of the eleven line items are understated.
Nobody has noticed. The client replied on Monday, saying thanks. His manager forwarded it to her manager with a nice comment.
Ted sits very still for about four minutes. Then he opens a new message and starts typing.
The clock started before anyone noticed
Here is the part people get wrong about mistakes at work. The damage clock does not start when someone catches you. It starts the moment you know.
Every hour you sit on it, the story changes underneath you. At 9:40 it is an error. By Thursday it is an error you knew about on Tuesday.
Those are two completely different conversations, and only one of them is survivable easily.
The founder of Planio wrote about handling mistakes on his own team, and his point is blunt. Most leaders care far more about what happens next than about the error itself.
There is a famous version of this. In 1978 the engineer William LeMessurier found a flaw in his newly built Citicorp tower in New York. A diagonal wind could topple it.
He took it to his clients, his insurers, and the city within weeks. The building was quietly reinforced at night while people worked in it.
He kept his reputation. Your pricing sheet is not a skyscraper, but the mechanism is identical. Speed is the only part of this you still control.
The four-part message
Write it in this order. The order matters more than the wording.
- What is wrong, in one sentence
- What it affects, specifically
- What you have already done
- What you need from them
Ted's version took him six minutes:
"The pricing sheet I sent Friday has an error. Two line items pulled from the wrong column and are understated by about 8%."
"Corrected version attached. I can send the client a short note today, or you can, whichever you prefer."
Read that again and notice what is doing the work. He arrived with the fix already made and one decision left for his manager.
That is the difference between reporting a problem and handing over a problem.
What to never put in it
Four things, all of which make the message worse.
- The first is a long apology. One line is plenty, and three make the error feel bigger than it is.
- The second is your explanation of how it happened. Save that for when someone asks. Right now it reads as an excuse, even when it is true.
- The third is anyone else's name, unless they need to act. "The template was already like that" might be accurate, and it will still land badly.
- The fourth is a promise you have not thought through. "This will never happen again" is not a plan.
Ted wrote a version with all four in it first. He deleted them and the message got shorter by half.
Send it to the right two people
Do not broadcast it. Do not tell only your closest colleague either, which is the version that feels safest and helps least.
Two groups need it: whoever is affected and whoever can help you fix it. That is usually your manager plus one other person.
Ted sent it to his manager and copied the account lead who talks to the client. Nobody else needed to know that morning.
The people who are affected need it so they do not find out sideways. The people who can help need it because you cannot always fix things alone.
Everybody else finding out is noise. It creates worry in people who have no action to take.
The 48-hour follow-up
This is the step almost everyone skips, and it is where the whole thing turns around.
Two days later, send one short message. Not another apology, and not a longer version of the first one.
"Quick follow-up on Friday's sheet. The client confirmed the corrected numbers. I've added a check on the column reference before anything goes out, so this specific error can't repeat."
Two sentences. What resolved, and what you changed so it does not come back.
This is what moves you from the person who made an error to the person who handles errors. Your manager will remember the second message far longer than the first.
Ted's manager replied with four words: "Good catch. Thanks for flagging."
Put the follow-up in your calendar when you send the first message. Two days later you will have moved on and forgotten.
When you find it and it is not yours
The same clock applies, with one change to the first sentence.
Do not open with who did it. Open with what is wrong and what you are proposing.
"The Q3 sheet has a formula error in two rows. Happy to fix it this morning if nobody else is on it."
You have flagged the problem and volunteered without accusing anyone. If someone needs to know whose it was, they will find out without your help.
This is also the version that makes people want to work with you. Nobody forgets who covered for them quietly.
Nine forty on a Tuesday
Ted still remembers the four minutes of sitting still. He says the temptation was not really to hide it.
The temptation was to wait until he understood exactly how it happened so he could explain himself properly.
That is the trap. Understanding can wait an afternoon. The message cannot.
He sent it at 9:46 with a gap in his own knowledge still open. His manager never once asked how it happened.
